Closed
Conversation
- Added rxLogState object and passiveRxTracking state variables - Created handlePassiveRxLogEvent() to parse all incoming packets - Implemented startPassiveRxListening() and stopPassiveRxListening() - Integrated passive listening into connected/disconnected handlers - Added RX Log UI section in index.html - Implemented all RX Log UI helper functions - Added future API integration placeholder - Added comprehensive debug logging throughout Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
- Added step 9 for passive RX listening in connection workflow - Updated high-level connection steps to include passive listening - Added passive RX stop in disconnection cleanup - Added comprehensive "Passive RX Log Listening" section - Documented key differences between active ping tracking and passive RX - Explained first hop vs last hop path interpretation - Documented UI components and future API integration - Updated summary with new design principle Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…ndards Add passive RX log listening for continuous repeater coverage monitoring
…ll RX messages Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…ash filter removal Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…ash-validation Disable channel hash filter in passive RX log to track all messages
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…er-function Remove redundant interval-based distance updater
… double decryption Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…gle handler Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…stener Refactor RX Log architecture: Unified handler eliminates Session Log duplicates
… window - Changed RX_LOG_LISTEN_WINDOW_MS from 7000ms to 10000ms (10 seconds) - Created new postApiInBackground() function for non-blocking API posts - Refactored sendPing() flow: timer starts immediately after RX window (doesn't wait for API) - Unlocked ping controls immediately after RX window completion - Moved status updates and next ping scheduling before API post - API success messages now suppressed from UI - API error messages shown only when background POST fails - 3-second delay and POST now run asynchronously - Updated debug logging to reflect new timing Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
- Updated STATUS_MESSAGES.md: Changed RX window duration from 7s to 10s - Deprecated "Posting to API" status message (now suppressed from UI) - Added new "Error: API post failed" status message documentation - Updated em dash timing (appears after RX window, not after API post) - Updated slot revocation flow to reflect background API posting - Added comprehensive "Ping/Repeat Listener Flow" section to CONNECTION_WORKFLOW.md - Documented old vs new flow comparison with benefits and timing analysis - Updated all references to reflect asynchronous API posting behavior Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…ndards-again Refactor ping/repeat flow: 10s RX window + async API posting
…and auto-ping logic guidelines
…e power reporting
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…delines Add SNR chip to Session Log summary and CSV export for all log sections
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…delines-again Move SNR chip from Session Log to RX Log and update CSV export formats
- Added REASON_MESSAGES constant mapping for extensible reason handling - Updated checkCapacity() to parse and store reason codes from API - Modified disconnect event handler to check REASON_MESSAGES first - Added fallback for unknown reason codes with generic message - Updated documentation in STATUS_MESSAGES.md and CONNECTION_WORKFLOW.md - Added debug logging for reason code processing Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…delines-another-one Add extensible reason code handling for capacity check API responses
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…delines-yet-again Optimize wardrive.js: Remove dead code, fix syntax error
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…delines-one-more-time Refactor: Consolidate duplicate log handling functions into reusable helpers
…logging-guidelines-one-more-time Revert "Refactor: Consolidate duplicate log handling functions into reusable helpers"
- Change debugWarn to debugError for all error conditions - Rename error messages for consistency and brevity - Update all "WarDriving" references to "MeshMapper" - Improve error message clarity and conciseness - Update documentation (STATUS_MESSAGES.md, CONNECTION_WORKFLOW.md) Co-authored-by: MrAlders0n <55921894+MrAlders0n@users.noreply.github.com>
…ndards Fix error logging and standardize error messages
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This release introduces significant improvements to the MeshCore GOME WarDriver app, including passive RX listening, an API batch queue system, enhanced logging capabilities, and comprehensive code optimization.
✨ New Features
Passive RX Listening & RX Log
API Batch Queue System
Error Log
CSV Export & Copy Buttons
🔧 Improvements
Ping/Repeat Listener Flow Optimization
postApiInBackground()runs silently, only showing errors if they occurCapacity Check API Enhancement
REASON_MESSAGESmapping allows easy addition of new reason codesStatus Messages Update
Debug Logging Enhancement
[BLE],[GPS],[PING],[API QUEUE], etc.)🧹 Code Cleanup
handlePassiveRxLogEvent(),startPassiveRxListening(),stopPassiveRxListening()index-new.html(237 lines)previewLength: 20in errorLogState)distanceUpdateTimerand related functions (distance updates now on GPS position changes)📚 Documentation